-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(cosmic-swingset): add metrics for each action type #10888
Conversation
bdd8e51
to
2af926f
Compare
Deploying agoric-sdk with Cloudflare Pages
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good so far. Let's try to figure out typing here.
691e465
to
1cb9440
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Curious to see why we don't need a @ts-expect-error
now that we have typing on actions.
not sure why, but it definitely does not complain:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR is blind to cosmos messages that aren't forwarded to cosmic-swingset. If the goal is a detailed cosmic-swingset perspective, then I think we should merge this metrics data into #10904 and report "cosmic_swingset_inbound_queue" data with both "queue" and "type" dimensional attributes.
I'm not sure what you mean here. Processed queued actions are indeed specific to messages that made it to cosmic-swingset in the first place through one of the queues.
While it's true that any action removed from one of the queue will be processed and accounted for here, I'm not sure we need to merge these 2 things. The type doesn't make much sense to track when decrementing the queue sizes because we never tracked the type when incrementing the queue size. Also, I'm not sure there is much benefit in tracking which queue a processed action came from. |
refs: #10883 Move the following action types into QueuedActionType definition: CALCULATE_FEES_IN_BEANS: 'CALCULATE_FEES_IN_BEANS', VTRANSFER_IBC_EVENT: 'VTRANSFER_IBC_EVENT', KERNEL_UPGRADE_EVENTS: 'KERNEL_UPGRADE_EVENTS',
refs: #10883 Add metrics for the follwoing action types: CALCULATE_FEES_IN_BEANS: 'CALCULATE_FEES_IN_BEANS', VTRANSFER_IBC_EVENT: 'VTRANSFER_IBC_EVENT', KERNEL_UPGRADE_EVENTS: 'KERNEL_UPGRADE_EVENTS',
refs: #10883 launch-chain.js: Generate actionMetrics dynamically from QueuedActionType action-types.js: Remove unused CALCULATE_FEES_IN_BEANS action type
Co-authored-by: Mathieu Hofman <[email protected]>
…tes of a single counter refs: #10883
Co-authored-by: Richard Gibson <[email protected]>
Co-authored-by: Richard Gibson <[email protected]>
1fa0ebf
to
6a3eeda
Compare
closes: #10883
refs: #10882
Description
Add metrics for the following action types:
Security Considerations
Metrics may expose inner state which could be used to mount an effective attack.
Scaling Considerations
No impact on a local node performance expected.
Documentation Considerations
Metric names and their meaning need to be documented as now available via standard reporting interface.
Testing Considerations
manual testing?
Upgrade Considerations
This will roll out as part of standard release.